Skip to content

Conversation

DaveHanns
Copy link
Contributor

@DaveHanns DaveHanns commented Oct 2, 2025

@DaveHanns DaveHanns requested review from B4nan and removed request for janbuchar and fnesveda October 2, 2025 11:25
@github-actions github-actions bot added this to the 124th sprint - Console team milestone Oct 2, 2025
@github-actions github-actions bot added the t-console Issues with this label are in the ownership of the console team. label Oct 2, 2025
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

Comment @cursor review or bugbot run to trigger another review on this PR

description: ''
nullable: true
defaultRunOptions:
oneOf:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: @B4nan, why do we declare the nullable fields in some cases like this ?
It results in a bit weird notation in docs, see screenshot.

image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no idea, the openapi schema was generated from apiary some time ago, could have been a quirk in the conversion script

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the actual type accepted by the API? Is it "DefaultRunOptions or null"?

I'm asking so that I can check out if there's a better way to express this. But you're right that this looks suspicious.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question ... it actually is not nullable, as setting DefaultRunOptions to null will fail both creation and update of the Actor.

So it case of update and create schema, it should be only optional, but not nullable 🤔
I guess not listing it in required but not setting it as nullable should be good enough.

Will try later.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Now it should better reflect the behaviour of the API.

Side note: I'm planning to revisit the DefaultRunOptions and make API accept partial DefaultRunOptions, so that user can specify only the defaults they actually want to customize and get our internal defaults for the rest.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool! Thanks for investigating 🙂

@apify-service-account
Copy link

Preview for this PR was built for commit d23946e7 and is ready at https://pr-1965.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit d2438661 and is ready at https://pr-1965.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit f67e6392 and is ready at https://pr-1965.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit cc55e577 and is ready at https://pr-1965.preview.docs.apify.com!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t-console Issues with this label are in the ownership of the console team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants